home *** CD-ROM | disk | FTP | other *** search
/ Danny Amor's Online Library / Danny Amor's Online Library - Volume 1.iso / html / rfc / rfcxxxx / rfc1657 < prev    next >
Text File  |  1995-07-26  |  46KB  |  1,180 lines
  1.  
  2.  
  3.  
  4.  
  5.  
  6.  
  7. Network Working Group                                          S. Willis
  8. Request for Comments: 1657                                    J. Burruss
  9. Category: Standards Track                  Wellfleet Communications Inc.
  10.                                                           J. Chu, Editor
  11.                                                                IBM Corp.
  12.                                                                July 1994
  13.  
  14.  
  15.       Definitions of Managed Objects for the Fourth Version of the
  16.               Border Gateway Protocol (BGP-4) using SMIv2
  17.  
  18. Status of this Memo
  19.  
  20.    This document specifies an Internet standards track protocol for the
  21.    Internet community, and requests discussion and suggestions for
  22.    improvements.  Please refer to the current edition of the "Internet
  23.    Official Protocol Standards" (STD 1) for the standardization state
  24.    and status of this protocol.  Distribution of this memo is unlimited.
  25.  
  26. 1. Introduction
  27.  
  28.    This memo defines a portion of the Management Information Base (MIB)
  29.    for use with network management protocols in the Internet community.
  30.    In particular, it describes managed objects used for managing the
  31.    Border Gateway Protocol Version 4 or lower [1, 2].
  32.  
  33. 2. The SNMPv2 Network Management Framework
  34.  
  35.    The SNMPv2 Network Management Framework consists of four major
  36.    components.  They are:
  37.  
  38.       RFC 1442 which defines the SMI, the mechanisms used for describing
  39.       and naming objects for the purpose of management.
  40.  
  41.       STD 17, RFC 1213 defines MIB-II, the core set of managed objects
  42.       forthe Internet suite of protocols.
  43.  
  44.       RFC 1445 which defines the administrative and other architectural
  45.       aspects of the framework.
  46.  
  47.       RFC 1448 which defines the protocol used for network access to
  48.       managed objects.
  49.  
  50.    The Framework permits new objects to be defined for the purpose of
  51.    experimentation and evaluation.
  52.  
  53.  
  54.  
  55.  
  56.  
  57.  
  58. Willis, Burruss & Chu                                           [Page 1]
  59.  
  60. RFC 1657                       BGP-4 MIB                       July 1994
  61.  
  62.  
  63. 3. Object Definitions
  64.  
  65.    Managed objects are accessed via a virtual information store, termed
  66.    the Management Information Base or MIB.  Objects in the MIB are
  67.    defined using the subset of Abstract Syntax Notation One (ASN.1)
  68.    defined in the SMI.  In particular, each object type is named by an
  69.    OBJECT IDENTIFIER, an administratively assigned name.  The object
  70.    type together with an object instance serves to uniquely identify a
  71.    specific instantiation of the object.  For human convenience, we
  72.    often use a textual string, termed the descriptor, to refer to the
  73.    object type.
  74.  
  75. 4. Overview
  76.  
  77.    These objects are used to control and manage a BGP-4 implementation.
  78.  
  79.    Apart from a few system-wide scalar objects, this MIB is broken into
  80.    three tables: the BGP Peer Table, the BGP Received Path Attribute
  81.    Table, and the BGP-4 Received Path Attribute Table. The BGP Peer
  82.    Table contains information about state and current activity of
  83.    connections with the BGP peers. The Received Path Attribute Table
  84.    contains path attributes received from all peers running BGP version
  85.    3 or less. The BGP-4 Received Path Attribute Table contains path
  86.    attributes received from all BGP-4 peers.  The actual attributes used
  87.    in determining a route are a subset of the received attribute tables
  88.    after local routing policy has been applied.
  89.  
  90. 5. Definitions
  91.  
  92. BGP4-MIB DEFINITIONS ::= BEGIN
  93.  
  94.                 IMPORTS
  95.                     MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
  96.                     IpAddress, Integer32, Counter32, Gauge32
  97.                         FROM SNMPv2-SMI
  98.                     mib-2
  99.                         FROM RFC1213-MIB;
  100.  
  101.                 bgp MODULE-IDENTITY
  102.                     LAST-UPDATED "9405050000Z"
  103.                     ORGANIZATION "IETF BGP Working Group"
  104.                     CONTACT-INFO
  105.                                 "   John Chu  (Editor)
  106.                             Postal: IBM Corp.
  107.                                     P.O.Box 218
  108.                                     Yorktown Heights, NY 10598
  109.                                     US
  110.  
  111.  
  112.  
  113.  
  114. Willis, Burruss & Chu                                           [Page 2]
  115.  
  116. RFC 1657                       BGP-4 MIB                       July 1994
  117.  
  118.  
  119.                                Tel: +1 914 945 3156
  120.                                Fax: +1 914 945 2141
  121.                             E-mail: jychu@watson.ibm.com"
  122.                         DESCRIPTION
  123.                                 "The MIB module for BGP-4."
  124.                     ::= { mib-2 15 }
  125.  
  126.                 bgpVersion OBJECT-TYPE
  127.                     SYNTAX     OCTET STRING (SIZE (1..255))
  128.                     MAX-ACCESS read-only
  129.                     STATUS     current
  130.                     DESCRIPTION
  131.                             "Vector of supported BGP protocol version
  132.                             numbers.  Each peer negotiates the version
  133.                             from this vector.  Versions are identified
  134.                             via the string of bits contained within this
  135.                             object.  The first octet contains bits 0 to
  136.                             7, the second octet contains bits 8 to 15,
  137.                             and so on, with the most significant bit
  138.                             referring to the lowest bit number in the
  139.                             octet (e.g., the MSB of the first octet
  140.                             refers to bit 0).  If a bit, i, is present
  141.                             and set, then the version (i+1) of the BGP
  142.                             is supported."
  143.                     ::= { bgp 1 }
  144.  
  145.                 bgpLocalAs OBJECT-TYPE
  146.                     SYNTAX     INTEGER (0..65535)
  147.                     MAX-ACCESS read-only
  148.                     STATUS     current
  149.                     DESCRIPTION
  150.                             "The local autonomous system number."
  151.                     ::= { bgp 2 }
  152.  
  153.  
  154.  
  155.                 -- BGP Peer table.  This table contains, one entry per
  156.                 -- BGP peer, information about the BGP peer.
  157.  
  158.                 bgpPeerTable OBJECT-TYPE
  159.                     SYNTAX     SEQUENCE OF BgpPeerEntry
  160.                     MAX-ACCESS not-accessible
  161.                     STATUS     current
  162.                     DESCRIPTION
  163.                             "BGP peer table.  This table contains,
  164.                             one entry per BGP peer, information about
  165.                             the connections with BGP peers."
  166.                     ::= { bgp 3 }
  167.  
  168.  
  169.  
  170. Willis, Burruss & Chu                                           [Page 3]
  171.  
  172. RFC 1657                       BGP-4 MIB                       July 1994
  173.  
  174.  
  175.                 bgpPeerEntry OBJECT-TYPE
  176.                     SYNTAX     BgpPeerEntry
  177.                     MAX-ACCESS not-accessible
  178.                     STATUS     current
  179.                     DESCRIPTION
  180.                             "Entry containing information about the
  181.                             connection with a BGP peer."
  182.                     INDEX { bgpPeerRemoteAddr }
  183.                     ::= { bgpPeerTable 1 }
  184.  
  185.                 BgpPeerEntry ::= SEQUENCE {
  186.                         bgpPeerIdentifier
  187.                             IpAddress,
  188.                         bgpPeerState
  189.                             INTEGER,
  190.                         bgpPeerAdminStatus
  191.                             INTEGER,
  192.                         bgpPeerNegotiatedVersion
  193.                             Integer32,
  194.                         bgpPeerLocalAddr
  195.                             IpAddress,
  196.                         bgpPeerLocalPort
  197.                             INTEGER,
  198.                         bgpPeerRemoteAddr
  199.                             IpAddress,
  200.                         bgpPeerRemotePort
  201.                             INTEGER,
  202.                         bgpPeerRemoteAs
  203.                             INTEGER,
  204.                         bgpPeerInUpdates
  205.                             Counter32,
  206.                         bgpPeerOutUpdates
  207.                             Counter32,
  208.                         bgpPeerInTotalMessages
  209.                             Counter32,
  210.                         bgpPeerOutTotalMessages
  211.                             Counter32,
  212.                         bgpPeerLastError
  213.                             OCTET STRING,
  214.                         bgpPeerFsmEstablishedTransitions
  215.                             Counter32,
  216.                         bgpPeerFsmEstablishedTime
  217.                             Gauge32,
  218.                         bgpPeerConnectRetryInterval
  219.                             INTEGER,
  220.                         bgpPeerHoldTime
  221.                             INTEGER,
  222.                         bgpPeerKeepAlive
  223.  
  224.  
  225.  
  226. Willis, Burruss & Chu                                           [Page 4]
  227.  
  228. RFC 1657                       BGP-4 MIB                       July 1994
  229.  
  230.  
  231.                             INTEGER,
  232.                         bgpPeerHoldTimeConfigured
  233.                             INTEGER,
  234.                         bgpPeerKeepAliveConfigured
  235.                             INTEGER,
  236.                         bgpPeerMinASOriginationInterval
  237.                             INTEGER,
  238.                         bgpPeerMinRouteAdvertisementInterval
  239.                             INTEGER,
  240.                         bgpPeerInUpdateElapsedTime
  241.                             Gauge32
  242.                         }
  243.  
  244.                 bgpPeerIdentifier OBJECT-TYPE
  245.                     SYNTAX     IpAddress
  246.                     MAX-ACCESS read-only
  247.                     STATUS     current
  248.                     DESCRIPTION
  249.                             "The BGP Identifier of this entry's BGP
  250.                             peer."
  251.                     ::= { bgpPeerEntry 1 }
  252.  
  253.                 bgpPeerState OBJECT-TYPE
  254.                     SYNTAX     INTEGER {
  255.                                         idle(1),
  256.                                         connect(2),
  257.                                         active(3),
  258.                                         opensent(4),
  259.                                         openconfirm(5),
  260.                                         established(6)
  261.                                }
  262.                     MAX-ACCESS read-only
  263.                     STATUS     current
  264.                     DESCRIPTION
  265.                             "The BGP peer connection state."
  266.                     ::= { bgpPeerEntry 2 }
  267.  
  268.                 bgpPeerAdminStatus OBJECT-TYPE
  269.                     SYNTAX     INTEGER {
  270.                                         stop(1),
  271.                                         start(2)
  272.                                }
  273.                     MAX-ACCESS read-write
  274.                     STATUS     current
  275.                     DESCRIPTION
  276.                             "The desired state of the BGP connection.
  277.                             A transition from 'stop' to 'start' will
  278.                             cause the BGP Start Event to be generated.
  279.  
  280.  
  281.  
  282. Willis, Burruss & Chu                                           [Page 5]
  283.  
  284. RFC 1657                       BGP-4 MIB                       July 1994
  285.  
  286.  
  287.                             A transition from 'start' to 'stop' will
  288.                             cause the BGP Stop Event to be generated.
  289.                             This parameter can be used to restart BGP
  290.                             peer connections.  Care should be used in
  291.                             providing write access to this object
  292.                             without adequate authentication."
  293.                     ::= { bgpPeerEntry 3 }
  294.  
  295.                 bgpPeerNegotiatedVersion OBJECT-TYPE
  296.                     SYNTAX     Integer32
  297.                     MAX-ACCESS read-only
  298.                     STATUS     current
  299.                     DESCRIPTION
  300.                             "The negotiated version of BGP running
  301.                             between the two peers."
  302.                     ::= { bgpPeerEntry 4 }
  303.  
  304.                 bgpPeerLocalAddr OBJECT-TYPE
  305.                     SYNTAX     IpAddress
  306.                     MAX-ACCESS read-only
  307.                     STATUS     current
  308.                     DESCRIPTION
  309.                             "The local IP address of this entry's BGP
  310.                             connection."
  311.                     ::= { bgpPeerEntry 5 }
  312.  
  313.                 bgpPeerLocalPort OBJECT-TYPE
  314.                     SYNTAX     INTEGER (0..65535)
  315.                     MAX-ACCESS read-only
  316.                     STATUS     current
  317.                     DESCRIPTION
  318.                             "The local port for the TCP connection
  319.                             between the BGP peers."
  320.                     ::= { bgpPeerEntry 6 }
  321.  
  322.                 bgpPeerRemoteAddr OBJECT-TYPE
  323.                     SYNTAX     IpAddress
  324.                     MAX-ACCESS read-only
  325.                     STATUS     current
  326.                     DESCRIPTION
  327.                             "The remote IP address of this entry's BGP
  328.                             peer."
  329.                     ::= { bgpPeerEntry 7 }
  330.  
  331.                 bgpPeerRemotePort OBJECT-TYPE
  332.                     SYNTAX     INTEGER (0..65535)
  333.                     MAX-ACCESS read-only
  334.                     STATUS     current
  335.  
  336.  
  337.  
  338. Willis, Burruss & Chu                                           [Page 6]
  339.  
  340. RFC 1657                       BGP-4 MIB                       July 1994
  341.  
  342.  
  343.                     DESCRIPTION
  344.                             "The remote port for the TCP connection
  345.                             between the BGP peers.  Note that the
  346.                             objects bgpPeerLocalAddr,
  347.                             bgpPeerLocalPort, bgpPeerRemoteAddr and
  348.                             bgpPeerRemotePort provide the appropriate
  349.                             reference to the standard MIB TCP
  350.                             connection table."
  351.                     ::= { bgpPeerEntry 8 }
  352.  
  353.                 bgpPeerRemoteAs OBJECT-TYPE
  354.                     SYNTAX     INTEGER (0..65535)
  355.                     MAX-ACCESS read-only
  356.                     STATUS     current
  357.                     DESCRIPTION
  358.                             "The remote autonomous system number."
  359.                     ::= { bgpPeerEntry 9 }
  360.  
  361.                 bgpPeerInUpdates OBJECT-TYPE
  362.                     SYNTAX     Counter32
  363.                     MAX-ACCESS read-only
  364.                     STATUS     current
  365.                     DESCRIPTION
  366.                             "The number of BGP UPDATE messages
  367.                             received on this connection.  This object
  368.                             should be initialized to zero (0) when the
  369.                             connection is established."
  370.                     ::= { bgpPeerEntry 10 }
  371.  
  372.                 bgpPeerOutUpdates OBJECT-TYPE
  373.                     SYNTAX     Counter32
  374.                     MAX-ACCESS read-only
  375.                     STATUS     current
  376.                     DESCRIPTION
  377.                             "The number of BGP UPDATE messages
  378.                             transmitted on this connection.  This
  379.                             object should be initialized to zero (0)
  380.                             when the connection is established."
  381.                     ::= { bgpPeerEntry 11 }
  382.  
  383.                 bgpPeerInTotalMessages OBJECT-TYPE
  384.                     SYNTAX     Counter32
  385.                     MAX-ACCESS read-only
  386.                     STATUS     current
  387.                     DESCRIPTION
  388.                             "The total number of messages received
  389.                             from the remote peer on this connection.
  390.                             This object should be initialized to zero
  391.  
  392.  
  393.  
  394. Willis, Burruss & Chu                                           [Page 7]
  395.  
  396. RFC 1657                       BGP-4 MIB                       July 1994
  397.  
  398.  
  399.                             when the connection is established."
  400.                     ::= { bgpPeerEntry 12 }
  401.  
  402.                 bgpPeerOutTotalMessages OBJECT-TYPE
  403.                     SYNTAX     Counter32
  404.                     MAX-ACCESS read-only
  405.                     STATUS     current
  406.                     DESCRIPTION
  407.                             "The total number of messages transmitted to
  408.                             the remote peer on this connection.  This
  409.                             object should be initialized to zero when
  410.                             the connection is established."
  411.                     ::= { bgpPeerEntry 13 }
  412.  
  413.                 bgpPeerLastError OBJECT-TYPE
  414.                     SYNTAX     OCTET STRING (SIZE (2))
  415.                     MAX-ACCESS read-only
  416.                     STATUS     current
  417.                     DESCRIPTION
  418.                             "The last error code and subcode seen by this
  419.                             peer on this connection.  If no error has
  420.                             occurred, this field is zero.  Otherwise, the
  421.                             first byte of this two byte OCTET STRING
  422.                             contains the error code, and the second byte
  423.                             contains the subcode."
  424.                     ::= { bgpPeerEntry 14 }
  425.  
  426.                 bgpPeerFsmEstablishedTransitions OBJECT-TYPE
  427.                     SYNTAX     Counter32
  428.                     MAX-ACCESS read-only
  429.                     STATUS     current
  430.                     DESCRIPTION
  431.                             "The total number of times the BGP FSM
  432.                             transitioned into the established state."
  433.                     ::= { bgpPeerEntry 15 }
  434.  
  435.                 bgpPeerFsmEstablishedTime OBJECT-TYPE
  436.                     SYNTAX     Gauge32
  437.                     MAX-ACCESS read-only
  438.                     STATUS     current
  439.                     DESCRIPTION
  440.                             "This timer indicates how long (in
  441.                             seconds) this peer has been in the
  442.                             Established state or how long
  443.                             since this peer was last in the
  444.                             Established state.  It is set to zero when
  445.                             a new peer is configured or the router is
  446.                             booted."
  447.  
  448.  
  449.  
  450. Willis, Burruss & Chu                                           [Page 8]
  451.  
  452. RFC 1657                       BGP-4 MIB                       July 1994
  453.  
  454.  
  455.                     ::= { bgpPeerEntry 16 }
  456.  
  457.                 bgpPeerConnectRetryInterval OBJECT-TYPE
  458.                     SYNTAX     INTEGER (1..65535)
  459.                     MAX-ACCESS read-write
  460.                     STATUS     current
  461.                     DESCRIPTION
  462.                             "Time interval in seconds for the
  463.                             ConnectRetry timer.  The suggested value
  464.                             for this timer is 120 seconds."
  465.                     ::= { bgpPeerEntry 17 }
  466.  
  467.                 bgpPeerHoldTime OBJECT-TYPE
  468.                     SYNTAX     INTEGER  ( 0 | 3..65535 )
  469.                     MAX-ACCESS read-only
  470.                     STATUS     current
  471.                     DESCRIPTION
  472.                             "Time interval in seconds for the Hold
  473.                             Timer established with the peer.  The
  474.                             value of this object is calculated by this
  475.                             BGP speaker by using the smaller of the
  476.                             value in bgpPeerHoldTimeConfigured and the
  477.                             Hold Time received in the OPEN message.
  478.                             This value must be at lease three seconds
  479.                             if it is not zero (0) in which case the
  480.                             Hold Timer has not been established with
  481.                             the peer, or, the value of
  482.                             bgpPeerHoldTimeConfigured is zero (0)."
  483.                     ::= { bgpPeerEntry 18 }
  484.  
  485.                 bgpPeerKeepAlive OBJECT-TYPE
  486.                     SYNTAX     INTEGER ( 0 | 1..21845 )
  487.                     MAX-ACCESS read-only
  488.                     STATUS     current
  489.                     DESCRIPTION
  490.                             "Time interval in seconds for the KeepAlive
  491.                             timer established with the peer.  The value
  492.                             of this object is calculated by this BGP
  493.                             speaker such that, when compared with
  494.                             bgpPeerHoldTime, it has the same
  495.                             proportion as what
  496.                             bgpPeerKeepAliveConfigured has when
  497.                             compared with bgpPeerHoldTimeConfigured.
  498.                             If the value of this object is zero (0),
  499.                             it indicates that the KeepAlive timer has
  500.                             not been established with the peer, or,
  501.                             the value of bgpPeerKeepAliveConfigured is
  502.                             zero (0)."
  503.  
  504.  
  505.  
  506. Willis, Burruss & Chu                                           [Page 9]
  507.  
  508. RFC 1657                       BGP-4 MIB                       July 1994
  509.  
  510.  
  511.                     ::= { bgpPeerEntry 19 }
  512.  
  513.                 bgpPeerHoldTimeConfigured OBJECT-TYPE
  514.                     SYNTAX     INTEGER ( 0 | 3..65535 )
  515.                     MAX-ACCESS read-write
  516.                     STATUS     current
  517.                     DESCRIPTION
  518.                             "Time interval in seconds for the Hold Time
  519.                             configured for this BGP speaker with this
  520.                             peer.  This value is placed in an OPEN
  521.                             message sent to this peer by this BGP
  522.                             speaker, and is compared with the Hold
  523.                             Time field in an OPEN message received
  524.                             from the peer when determining the Hold
  525.                             Time (bgpPeerHoldTime) with the peer.
  526.                             This value must not be less than three
  527.                             seconds if it is not zero (0) in which
  528.                             case the Hold Time is NOT to be
  529.                             established with the peer.  The suggested
  530.                             value for this timer is 90 seconds."
  531.                     ::= { bgpPeerEntry 20 }
  532.  
  533.                 bgpPeerKeepAliveConfigured OBJECT-TYPE
  534.                     SYNTAX     INTEGER ( 0 | 1..21845 )
  535.                     MAX-ACCESS read-write
  536.                     STATUS     current
  537.                     DESCRIPTION
  538.                             "Time interval in seconds for the
  539.                             KeepAlive timer configured for this BGP
  540.                             speaker with this peer.  The value of this
  541.                             object will only determine the
  542.                             KEEPALIVE messages' frequency relative to
  543.                             the value specified in
  544.                             bgpPeerHoldTimeConfigured; the actual
  545.                             time interval for the KEEPALIVE messages
  546.                             is indicated by bgpPeerKeepAlive.  A
  547.                             reasonable maximum value for this timer
  548.                             would be configured to be one
  549.                             third of that of
  550.                             bgpPeerHoldTimeConfigured.
  551.                             If the value of this object is zero (0),
  552.                             no periodical KEEPALIVE messages are sent
  553.                             to the peer after the BGP connection has
  554.                             been established.  The suggested value for
  555.                             this timer is 30 seconds."
  556.                     ::= { bgpPeerEntry 21 }
  557.  
  558.  
  559.  
  560.  
  561.  
  562. Willis, Burruss & Chu                                          [Page 10]
  563.  
  564. RFC 1657                       BGP-4 MIB                       July 1994
  565.  
  566.  
  567.                 bgpPeerMinASOriginationInterval OBJECT-TYPE
  568.                     SYNTAX     INTEGER (1..65535)
  569.                     MAX-ACCESS read-write
  570.                     STATUS     current
  571.                     DESCRIPTION
  572.                             "Time interval in seconds for the
  573.                             MinASOriginationInterval timer.
  574.                             The suggested value for this timer is 15
  575.                             seconds."
  576.                     ::= { bgpPeerEntry 22 }
  577.  
  578.                 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE
  579.                     SYNTAX     INTEGER (1..65535)
  580.                     MAX-ACCESS read-write
  581.                     STATUS     current
  582.                     DESCRIPTION
  583.                             "Time interval in seconds for the
  584.                             MinRouteAdvertisementInterval timer.
  585.                             The suggested value for this timer is 30
  586.                             seconds."
  587.                     ::= { bgpPeerEntry 23 }
  588.  
  589.                 bgpPeerInUpdateElapsedTime OBJECT-TYPE
  590.                     SYNTAX     Gauge32
  591.                     MAX-ACCESS read-only
  592.                     STATUS     current
  593.                     DESCRIPTION
  594.                             "Elapsed time in seconds since the last BGP
  595.                             UPDATE message was received from the peer.
  596.                             Each time bgpPeerInUpdates is incremented,
  597.                             the value of this object is set to zero
  598.                             (0)."
  599.                     ::= { bgpPeerEntry 24 }
  600.  
  601.  
  602.  
  603.                 bgpIdentifier OBJECT-TYPE
  604.                     SYNTAX     IpAddress
  605.                     MAX-ACCESS read-only
  606.                     STATUS     current
  607.                     DESCRIPTION
  608.                             "The BGP Identifier of local system."
  609.                     ::= { bgp 4 }
  610.  
  611.  
  612.  
  613.  
  614.  
  615.  
  616.  
  617.  
  618. Willis, Burruss & Chu                                          [Page 11]
  619.  
  620. RFC 1657                       BGP-4 MIB                       July 1994
  621.  
  622.  
  623.                 -- Received Path Attribute Table.  This table contains,
  624.                 -- one entry per path to a network, path attributes
  625.                 -- received from all peers running BGP version 3 or
  626.                 -- less.  This table is deprecated.
  627.  
  628.                 bgpRcvdPathAttrTable OBJECT-TYPE
  629.                     SYNTAX     SEQUENCE OF BgpPathAttrEntry
  630.                     MAX-ACCESS not-accessible
  631.                     STATUS     obsolete
  632.                     DESCRIPTION
  633.                             "The BGP Received Path Attribute Table
  634.                             contains information about paths to
  635.                             destination networks received from all
  636.                             peers running BGP version 3 or less."
  637.                     ::= { bgp 5 }
  638.  
  639.                 bgpPathAttrEntry OBJECT-TYPE
  640.                     SYNTAX     BgpPathAttrEntry
  641.                     MAX-ACCESS not-accessible
  642.                     STATUS     obsolete
  643.                     DESCRIPTION
  644.                             "Information about a path to a network."
  645.                     INDEX { bgpPathAttrDestNetwork,
  646.                             bgpPathAttrPeer        }
  647.                     ::= { bgpRcvdPathAttrTable 1 }
  648.  
  649.                 BgpPathAttrEntry ::= SEQUENCE {
  650.                     bgpPathAttrPeer
  651.                          IpAddress,
  652.                     bgpPathAttrDestNetwork
  653.                          IpAddress,
  654.                     bgpPathAttrOrigin
  655.                          INTEGER,
  656.                     bgpPathAttrASPath
  657.                          OCTET STRING,
  658.                     bgpPathAttrNextHop
  659.                          IpAddress,
  660.                     bgpPathAttrInterASMetric
  661.                          Integer32
  662.                 }
  663.  
  664.                 bgpPathAttrPeer OBJECT-TYPE
  665.                     SYNTAX     IpAddress
  666.                     MAX-ACCESS read-only
  667.                     STATUS     obsolete
  668.                     DESCRIPTION
  669.                             "The IP address of the peer where the path
  670.                             information was learned."
  671.  
  672.  
  673.  
  674. Willis, Burruss & Chu                                          [Page 12]
  675.  
  676. RFC 1657                       BGP-4 MIB                       July 1994
  677.  
  678.  
  679.                     ::= { bgpPathAttrEntry 1 }
  680.  
  681.                 bgpPathAttrDestNetwork OBJECT-TYPE
  682.                     SYNTAX     IpAddress
  683.                     MAX-ACCESS read-only
  684.                     STATUS     obsolete
  685.                     DESCRIPTION
  686.                             "The address of the destination network."
  687.                     ::= { bgpPathAttrEntry 2 }
  688.  
  689.                 bgpPathAttrOrigin OBJECT-TYPE
  690.                     SYNTAX     INTEGER {
  691.                                    igp(1),-- networks are interior
  692.                                    egp(2),-- networks learned via EGP
  693.                                    incomplete(3) -- undetermined
  694.                                }
  695.                     MAX-ACCESS read-only
  696.                     STATUS     obsolete
  697.                     DESCRIPTION
  698.                          "The ultimate origin of the path information."
  699.                     ::= { bgpPathAttrEntry 3 }
  700.  
  701.                 bgpPathAttrASPath OBJECT-TYPE
  702.                     SYNTAX     OCTET STRING (SIZE (2..255))
  703.                     MAX-ACCESS read-only
  704.                     STATUS     obsolete
  705.                     DESCRIPTION
  706.                             "The set of ASs that must be traversed to
  707.                             reach the network.  This object is
  708.                             probably best represented as SEQUENCE OF
  709.                             INTEGER.  For SMI compatibility, though,
  710.                             it is represented as OCTET STRING.  Each
  711.                             AS is represented as a pair of octets
  712.                             according to the following algorithm:
  713.  
  714.                                 first-byte-of-pair = ASNumber / 256;
  715.                                 second-byte-of-pair = ASNumber & 255;"
  716.                     ::= { bgpPathAttrEntry 4 }
  717.  
  718.                 bgpPathAttrNextHop OBJECT-TYPE
  719.                     SYNTAX     IpAddress
  720.                     MAX-ACCESS read-only
  721.                     STATUS     obsolete
  722.                     DESCRIPTION
  723.                             "The address of the border router that
  724.                             should be used for the destination
  725.                             network."
  726.                     ::= { bgpPathAttrEntry 5 }
  727.  
  728.  
  729.  
  730. Willis, Burruss & Chu                                          [Page 13]
  731.  
  732. RFC 1657                       BGP-4 MIB                       July 1994
  733.  
  734.  
  735.                 bgpPathAttrInterASMetric OBJECT-TYPE
  736.                     SYNTAX     Integer32
  737.                     MAX-ACCESS read-only
  738.                     STATUS     obsolete
  739.                     DESCRIPTION
  740.                             "The optional inter-AS metric.  If this
  741.                             attribute has not been provided for this
  742.                             route, the value for this object is 0."
  743.                     ::= { bgpPathAttrEntry 6 }
  744.  
  745.  
  746.  
  747.                 -- BGP-4 Received Path Attribute Table.  This table
  748.                 -- contains, one entry per path to a network, path
  749.                 -- attributes received from all peers running BGP-4.
  750.  
  751.                 bgp4PathAttrTable OBJECT-TYPE
  752.                     SYNTAX     SEQUENCE OF Bgp4PathAttrEntry
  753.                     MAX-ACCESS not-accessible
  754.                     STATUS     current
  755.                     DESCRIPTION
  756.                             "The BGP-4 Received Path Attribute Table
  757.                             contains information about paths to
  758.                             destination networks received from all
  759.                             BGP4 peers."
  760.                     ::= { bgp 6 }
  761.  
  762.                 bgp4PathAttrEntry OBJECT-TYPE
  763.                     SYNTAX     Bgp4PathAttrEntry
  764.                     MAX-ACCESS not-accessible
  765.                     STATUS     current
  766.                     DESCRIPTION
  767.                             "Information about a path to a network."
  768.                     INDEX { bgp4PathAttrIpAddrPrefix,
  769.                             bgp4PathAttrIpAddrPrefixLen,
  770.                             bgp4PathAttrPeer            }
  771.                     ::= { bgp4PathAttrTable 1 }
  772.  
  773.                 Bgp4PathAttrEntry ::= SEQUENCE {
  774.                     bgp4PathAttrPeer
  775.                          IpAddress,
  776.                     bgp4PathAttrIpAddrPrefixLen
  777.                          INTEGER,
  778.                     bgp4PathAttrIpAddrPrefix
  779.                          IpAddress,
  780.                     bgp4PathAttrOrigin
  781.                          INTEGER,
  782.                     bgp4PathAttrASPathSegment
  783.  
  784.  
  785.  
  786. Willis, Burruss & Chu                                          [Page 14]
  787.  
  788. RFC 1657                       BGP-4 MIB                       July 1994
  789.  
  790.  
  791.                          OCTET STRING,
  792.                     bgp4PathAttrNextHop
  793.                          IpAddress,
  794.                     bgp4PathAttrMultiExitDisc
  795.                          INTEGER,
  796.                     bgp4PathAttrLocalPref
  797.                          INTEGER,
  798.                     bgp4PathAttrAtomicAggregate
  799.                          INTEGER,
  800.                     bgp4PathAttrAggregatorAS
  801.                          INTEGER,
  802.                     bgp4PathAttrAggregatorAddr
  803.                          IpAddress,
  804.                     bgp4PathAttrCalcLocalPref
  805.                          INTEGER,
  806.                     bgp4PathAttrBest
  807.                          INTEGER,
  808.                     bgp4PathAttrUnknown
  809.                          OCTET STRING
  810.  
  811.                 }
  812.  
  813.                 bgp4PathAttrPeer OBJECT-TYPE
  814.                     SYNTAX     IpAddress
  815.                     MAX-ACCESS read-only
  816.                     STATUS     current
  817.                     DESCRIPTION
  818.                             "The IP address of the peer where the path
  819.                             information was learned."
  820.                     ::= { bgp4PathAttrEntry 1 }
  821.  
  822.                 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE
  823.                     SYNTAX     INTEGER (0..32)
  824.                     MAX-ACCESS read-only
  825.                     STATUS     current
  826.                     DESCRIPTION
  827.                             "Length in bits of the IP address prefix
  828.                             in the Network Layer Reachability
  829.                             Information field."
  830.                     ::= { bgp4PathAttrEntry 2 }
  831.  
  832.                 bgp4PathAttrIpAddrPrefix OBJECT-TYPE
  833.                     SYNTAX     IpAddress
  834.                     MAX-ACCESS read-only
  835.                     STATUS     current
  836.                     DESCRIPTION
  837.                             "An IP address prefix in the Network Layer
  838.                             Reachability Information field.  This object
  839.  
  840.  
  841.  
  842. Willis, Burruss & Chu                                          [Page 15]
  843.  
  844. RFC 1657                       BGP-4 MIB                       July 1994
  845.  
  846.  
  847.                             is an IP address containing the prefix with
  848.                             length specified by
  849.                             bgp4PathAttrIpAddrPrefixLen.
  850.                             Any bits beyond the length specified by
  851.                             bgp4PathAttrIpAddrPrefixLen are zeroed."
  852.                     ::= { bgp4PathAttrEntry 3 }
  853.  
  854.                 bgp4PathAttrOrigin OBJECT-TYPE
  855.                     SYNTAX     INTEGER {
  856.                                          igp(1),-- networks are interior
  857.                                          egp(2),-- networks learned
  858.                                                 -- via EGP
  859.                                          incomplete(3) -- undetermined
  860.                                        }
  861.                     MAX-ACCESS read-only
  862.                     STATUS     current
  863.                     DESCRIPTION
  864.                             "The ultimate origin of the path
  865.                             information."
  866.                     ::= { bgp4PathAttrEntry 4 }
  867.  
  868.                 bgp4PathAttrASPathSegment OBJECT-TYPE
  869.                     SYNTAX     OCTET STRING (SIZE (2..255))
  870.                     MAX-ACCESS read-only
  871.                     STATUS     current
  872.                     DESCRIPTION
  873.                             "The sequence of AS path segments.  Each AS
  874.                             path segment is represented by a triple
  875.                             <type, length, value>.
  876.  
  877.                             The type is a 1-octet field which has two
  878.                             possible values:
  879.                                  1      AS_SET: unordered set of ASs a
  880.                                              route in the UPDATE
  881.                                              message has traversed
  882.                                  2      AS_SEQUENCE: ordered set of ASs
  883.                                              a route in the UPDATE
  884.                                              message has traversed.
  885.  
  886.                             The length is a 1-octet field containing the
  887.                             number of ASs in the value field.
  888.  
  889.                             The value field contains one or more AS
  890.                             numbers, each AS is represented in the octet
  891.                             string as a pair of octets according to the
  892.                             following algorithm:
  893.  
  894.  
  895.  
  896.  
  897.  
  898. Willis, Burruss & Chu                                          [Page 16]
  899.  
  900. RFC 1657                       BGP-4 MIB                       July 1994
  901.  
  902.  
  903.                                 first-byte-of-pair = ASNumber / 256;
  904.                                 second-byte-of-pair = ASNumber & 255;"
  905.                     ::= { bgp4PathAttrEntry 5 }
  906.  
  907.                 bgp4PathAttrNextHop OBJECT-TYPE
  908.                     SYNTAX     IpAddress
  909.                     MAX-ACCESS read-only
  910.                     STATUS     current
  911.                     DESCRIPTION
  912.                             "The address of the border router that
  913.                             should be used for the destination
  914.                             network."
  915.                     ::= { bgp4PathAttrEntry 6 }
  916.  
  917.                 bgp4PathAttrMultiExitDisc OBJECT-TYPE
  918.                     SYNTAX     INTEGER (-1..2147483647)
  919.                     MAX-ACCESS read-only
  920.                     STATUS     current
  921.                     DESCRIPTION
  922.                             "This metric is used to discriminate
  923.                             between multiple exit points to an
  924.                             adjacent autonomous system.  A value of -1
  925.                             indicates the absence of this attribute."
  926.                     ::= { bgp4PathAttrEntry 7 }
  927.  
  928.                 bgp4PathAttrLocalPref OBJECT-TYPE
  929.                     SYNTAX     INTEGER (-1..2147483647)
  930.                     MAX-ACCESS read-only
  931.                     STATUS     current
  932.                     DESCRIPTION
  933.                             "The originating BGP4 speaker's degree of
  934.                             preference for an advertised route.  A
  935.                             value of -1 indicates the absence of this
  936.                             attribute."
  937.                     ::= { bgp4PathAttrEntry 8 }
  938.  
  939.                 bgp4PathAttrAtomicAggregate OBJECT-TYPE
  940.                     SYNTAX     INTEGER {
  941.                                    lessSpecificRrouteNotSelected(1),
  942.                                    lessSpecificRouteSelected(2)
  943.                                }
  944.                     MAX-ACCESS read-only
  945.                     STATUS     current
  946.                     DESCRIPTION
  947.                             "Whether or not the local system has
  948.                             selected a less specific route without
  949.                             selecting a more specific route."
  950.                     ::= { bgp4PathAttrEntry 9 }
  951.  
  952.  
  953.  
  954. Willis, Burruss & Chu                                          [Page 17]
  955.  
  956. RFC 1657                       BGP-4 MIB                       July 1994
  957.  
  958.  
  959.                 bgp4PathAttrAggregatorAS OBJECT-TYPE
  960.                     SYNTAX     INTEGER (0..65535)
  961.                     MAX-ACCESS read-only
  962.                     STATUS     current
  963.                     DESCRIPTION
  964.                             "The AS number of the last BGP4 speaker that
  965.                             performed route aggregation.  A value of
  966.                             zero (0) indicates the absence of this
  967.                             attribute."
  968.                     ::= { bgp4PathAttrEntry 10 }
  969.  
  970.                 bgp4PathAttrAggregatorAddr OBJECT-TYPE
  971.                     SYNTAX     IpAddress
  972.                     MAX-ACCESS read-only
  973.                     STATUS     current
  974.                     DESCRIPTION
  975.                             "The IP address of the last BGP4 speaker
  976.                             that performed route aggregation.  A value
  977.                             of 0.0.0.0 indicates the absence of this
  978.                             attribute."
  979.                     ::= { bgp4PathAttrEntry 11 }
  980.  
  981.                 bgp4PathAttrCalcLocalPref OBJECT-TYPE
  982.                     SYNTAX     INTEGER (-1..2147483647)
  983.                     MAX-ACCESS read-only
  984.                     STATUS     current
  985.                     DESCRIPTION
  986.                             "The degree of preference calculated by the
  987.                             receiving BGP4 speaker for an advertised
  988.                             route.  A value of -1 indicates the
  989.                             absence of this attribute."
  990.                     ::= { bgp4PathAttrEntry 12 }
  991.  
  992.                 bgp4PathAttrBest OBJECT-TYPE
  993.                     SYNTAX     INTEGER {
  994.                                    false(1),-- not chosen as best route
  995.                                    true(2) -- chosen as best route
  996.                                }
  997.                     MAX-ACCESS read-only
  998.                     STATUS     current
  999.                     DESCRIPTION
  1000.                             "An indication of whether or not this route
  1001.                             was chosen as the best BGP4 route."
  1002.                     ::= { bgp4PathAttrEntry 13 }
  1003.  
  1004.                bgp4PathAttrUnknown OBJECT-TYPE
  1005.                     SYNTAX     OCTET STRING (SIZE(0..255))
  1006.                     MAX-ACCESS read-only
  1007.  
  1008.  
  1009.  
  1010. Willis, Burruss & Chu                                          [Page 18]
  1011.  
  1012. RFC 1657                       BGP-4 MIB                       July 1994
  1013.  
  1014.  
  1015.                     STATUS     current
  1016.                     DESCRIPTION
  1017.                             "One or more path attributes not understood
  1018.                              by this BGP4 speaker.  Size zero (0)
  1019.                              indicates the absence of such
  1020.                              attribute(s).  Octets beyond the maximum
  1021.                              size, if any, are not recorded by this
  1022.                              object."
  1023.                     ::= { bgp4PathAttrEntry 14 }
  1024.  
  1025.  
  1026.                 -- Traps.
  1027.  
  1028.                 bgpTraps                OBJECT IDENTIFIER ::= { bgp 7 }
  1029.  
  1030.                 bgpEstablished NOTIFICATION-TYPE
  1031.                     OBJECTS { bgpPeerLastError,
  1032.                               bgpPeerState      }
  1033.                     STATUS  current
  1034.                     DESCRIPTION
  1035.                             "The BGP Established event is generated when
  1036.                             the BGP FSM enters the ESTABLISHED state."
  1037.                     ::= { bgpTraps 1 }
  1038.  
  1039.                 bgpBackwardTransition NOTIFICATION-TYPE
  1040.                     OBJECTS { bgpPeerLastError,
  1041.                               bgpPeerState      }
  1042.                     STATUS  current
  1043.                     DESCRIPTION
  1044.                             "The BGPBackwardTransition Event is generated
  1045.                             when the BGP FSM moves from a higher numbered
  1046.                             state to a lower numbered state."
  1047.                     ::= { bgpTraps 2 }
  1048.  
  1049. END
  1050.  
  1051.  
  1052.  
  1053.  
  1054.  
  1055.  
  1056.  
  1057.  
  1058.  
  1059.  
  1060.  
  1061.  
  1062.  
  1063.  
  1064.  
  1065.  
  1066. Willis, Burruss & Chu                                          [Page 19]
  1067.  
  1068. RFC 1657                       BGP-4 MIB                       July 1994
  1069.  
  1070.  
  1071. 6. Acknowledgements
  1072.  
  1073.    We would like to acknowledge the assistance of all the members of the
  1074.    Interconnectivity Working Group, and particularly the following
  1075.    individuals:
  1076.  
  1077.         Yakov Rekhter, IBM
  1078.         Rob Coltun, University of Maryland
  1079.         Guy Almes, ANS
  1080.         Jeff Honig, Cornell Theory Center
  1081.         Marshall T. Rose, Dover Beach Consulting, Inc.
  1082.         Dennis Ferguson, ANS
  1083.         Mike Mathis, PSC
  1084.         John Krawczyk, Wellfleet Communications Inc.
  1085.         Curtis Villamizar, ANS
  1086.         Dave LeRoy, Pencom Systems
  1087.         Paul Traina, cisco Systems
  1088.         Andrew Partan, UUNET
  1089.         Robert Snyder, cisco Systems
  1090.         Dimitry Haskin, Wellfleet Communications Inc.
  1091.         Peder Chr Norgaard, Telebit Communications A/S
  1092.         Joel Halpern, Network Systems Corporation
  1093.  
  1094. 7. References
  1095.  
  1096.    [1] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 (BGP-4)",
  1097.        RFC 1654,  T.J. Watson Research Center, IBM Corp., cisco Systems,
  1098.        July 1994.
  1099.  
  1100.    [2] Rekhter, Y., and P. Gross, Editors, "Application of the Border
  1101.        Gateway Protocol in the Internet", RFC 1655 T.J. Watson Research
  1102.        Center, IBM Corp., MCI, July 1994.
  1103.  
  1104. 8. Security Considerations
  1105.  
  1106.    Security issues are not discussed in this memo.
  1107.  
  1108.  
  1109.  
  1110.  
  1111.  
  1112.  
  1113.  
  1114.  
  1115.  
  1116.  
  1117.  
  1118.  
  1119.  
  1120.  
  1121.  
  1122. Willis, Burruss & Chu                                          [Page 20]
  1123.  
  1124. RFC 1657                       BGP-4 MIB                       July 1994
  1125.  
  1126.  
  1127. 9.  Authors' Addresses
  1128.  
  1129.    Steven Willis
  1130.    Wellfleet Communications Inc.
  1131.    15 Crosby Drive
  1132.    Bedford, MA 01730
  1133.  
  1134.    Phone: (617) 275-2400
  1135.    EMail: swillis@wellfleet.com
  1136.  
  1137.  
  1138.    John Burruss
  1139.    Wellfleet Communications Inc.
  1140.    15 Crosby Drive
  1141.    Bedford, MA 01730
  1142.  
  1143.    Phone: (617) 275-2400
  1144.    EMail: jburruss@wellfleet.com
  1145.  
  1146.  
  1147.    John Chu
  1148.    IBM Corp.
  1149.    P.O.Box 218
  1150.    Yorktown Heights, NY 10598
  1151.  
  1152.    Phone: (914) 945-3156
  1153.    EMail: jychu@watson.ibm.com
  1154.  
  1155.  
  1156.  
  1157.  
  1158.  
  1159.  
  1160.  
  1161.  
  1162.  
  1163.  
  1164.  
  1165.  
  1166.  
  1167.  
  1168.  
  1169.  
  1170.  
  1171.  
  1172.  
  1173.  
  1174.  
  1175.  
  1176.  
  1177.  
  1178. Willis, Burruss & Chu                                          [Page 21]
  1179.  
  1180.